What Consistency Does Your Key-Value Store Actually Provide?

Many key-value stores have recently been proposed as platforms for always-on, globally-distributed, Internetscale applications. To meet their needs, these stores often sacrifice consistency for availability. Yet, few tools exist that can verify the consistency actually provided by a key-value store, and quantify the violations if any. How can a user check if a storage system meets its promise of consistency? If a system only promises eventual consistency, how bad is it really? In this paper, we present efficient algorithms that help answer these questions. By analyzing the trace of interactions between the client machines and a key-value store, the algorithms can report whether the trace is safe, regular, or atomic, and if not, how many violations there are in the trace. We run these algorithms on traces of our eventually consistent keyvalue store called Pahoehoe and find few or no violations, thus showing that it often behaves like a strongly consistent system during our tests.